Hi All,

I am trying to troubleshoot an issue with calls being dropped, and have noticed that on some of my dropped calls I see the following in the BYE message:

ms-diagnostics: 10026;source="Lync.domain.local";reason="This call leg has been replaced";component="MediationServer"
ms-diagnostics-public: 10026;reason="This call leg has been replaced";component="MediationServer"
ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet

The call path is PSTN-->Gateway-->Lync-->Trusted application Server-->Agent

I cant seem to find much on what the "This call leg has been replaced" message means, if anyone can help me out it would be appreciated.

Cheers

J

Unfortunately, I will need a little more information on what is being done here. Is this a native Lync application?  Is this a third party application or a UCCPAPI built application? If not, are you calling a RGS workgroup? A high level overview of what you are trying to accomplish might help me get you an answer to your question.  

Hi JMH79,

 

Did you ever have any luck in resolving this issue?  I am in a simialr situation with a Lync system dropping calls.  In my case the scenario is as follows:-

BRI Call inbound > Avaya Gateway Remote Site > MPLS Link > Avaya CM/Session Manager > Lync Response Group > MPLS > Users in Remote Site (same as BRI).

I see from Lync that the call is presented to the three users in the RG.  I then get this message 2 seconds later (in the example I'm reviewing) to say that the call leg has been replaced.  The user experience is that the call drops if in voice or stops ringing if voice has not been established.

 

Many thanks in advance for any assistance

 

I too am having a similar issue. The calls that are reported to me are longer in duration than a couple of seconds. The last call reported as dropped was at the 00:02:26 mark in the call. The Diagnostic ID is

10026;
source="server-FQDN"; reason="This call leg has been replaced"; component="MediationServer"

Lync 2010 CU-4

I'm using an Audio Codes Mediant 1000 Gateway

Polycom CX600 Phone.

Any insight here would be much appreciated.

All,

I have been investigating some reports from users where calls have been dropped.

I have run a query against the monitoring DB and can see that the reported occasions have the same errors logged.

Daignostic code: 10026

This call leg has been replaced

This call leg has been replaced by an INVITE with replaces

I am also using a Audio Codes Mediant 1000 gateway running firmware version 6.40A.025.001.

Name              : Microsoft Lync Server 2010, Mediation Server
Version           : 4.0.7577.183

Has anyone been able to determine the cause of this problem? Are all of them related to Audio Code Mediant gateways? If so what version are you all running.

Thanks for your assistance.

Ben

Hi,

This doesnt seem to have an answer?

Diagnostic ID - 10026

Why are these calls dropping out I seem to have heaps.

If someone could help this would be great.

Thanks

All,

I have now had some time to analyse the problem further. I have produced a more detailed way of reviewing the data. By using a custom SQL view (see attached) in the LCSCDR DB I can now connect Excel to the database and using Power Pivot quickly breakdown the data and look for some form of trend. Now I can see a the precise time, client versions and affected users. I have compared this information with the Syslog outputs on the Audio Codes gateway.

It seems that all the problems I have generally occur when clients are connected to only one of my front end servers. There does not appear to be a similar number of problems on the other one.

Can anyone else please confirm if they too have an Audio Codes gateway when suffering with this issue?

I now have CU6 applied to all of the Lync infrastructure. This has not resolved the problem but has reduced the frequency which the errors are occurring.

Does anyone else have any further thoughts on this?

Thanks

Ben

All,

Another thing to ask you all....

Are a majority of your errors to the User2Client type of "RTCC/4.0.0.0 Response_Group_Service" ?

Regards

Ben

Hi all
Did you find a solution here?

I do have the same error in Lync 2013

My problem is that 3 out 4 RGS work perfect but on on the last i do receive that above message

Regards

Henrik B